Skip to content

feat(health): support various policies _.microgateway.airlock.com#28268

Open
root30 wants to merge 3 commits into
argoproj:masterfrom
root30:resource-customizations-microgateway-policies
Open

feat(health): support various policies _.microgateway.airlock.com#28268
root30 wants to merge 3 commits into
argoproj:masterfrom
root30:resource-customizations-microgateway-policies

Conversation

@root30

@root30 root30 commented Jun 12, 2026

Copy link
Copy Markdown

This PR adds the custom health check for various policy Types of Airlock Microgateway.

Checklist:

  • Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
  • The title of the PR states what changed and the related issues number (used for the release note).
  • The title of the PR conforms to the Title of the PR
  • I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
  • I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
  • Does this PR require documentation updates?
  • I've updated documentation as required by this PR.
  • I have signed off all my commits as required by DCO
  • I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
  • My build is green (troubleshooting builds).
  • My new feature complies with the feature status guidelines.
  • I have added a brief description of why this PR is necessary and/or what this PR solves.
  • Optional. My organization is added to USERS.md.
  • Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).

@bunnyshell

bunnyshell Bot commented Jun 12, 2026

Copy link
Copy Markdown

🔴 Preview Environment stopped on Bunnyshell

See: Environment Details | Pipeline Logs

Available commands (reply to this comment):

  • 🔵 /bns:start to start the environment
  • 🚀 /bns:deploy to redeploy the environment
  • /bns:delete to remove the environment

@codecov

codecov Bot commented Jun 12, 2026

Copy link
Copy Markdown

Bundle Report

Bundle size has no change ✅

@root30 root30 force-pushed the resource-customizations-microgateway-policies branch from 016b61e to 90bd417 Compare June 12, 2026 12:45
@root30 root30 marked this pull request as ready for review June 12, 2026 12:45
@root30 root30 requested a review from a team as a code owner June 12, 2026 12:45
@codecov

codecov Bot commented Jun 12, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (master@0fb522b). Learn more about missing BASE report.

Additional details and impacted files
@@            Coverage Diff            @@
##             master   #28268   +/-   ##
=========================================
  Coverage          ?   65.05%           
=========================================
  Files             ?      425           
  Lines             ?    59292           
  Branches          ?        0           
=========================================
  Hits              ?    38575           
  Misses            ?    17147           
  Partials          ?     3570           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

Comment thread resource_customizations/microgateway.airlock.com/_/health.lua
Signed-off-by: Roman Willi <roman.willi@ergon.ch>
@root30 root30 force-pushed the resource-customizations-microgateway-policies branch from 5632d45 to c8d02c1 Compare June 15, 2026 07:37
… microgateway.airlock.com API group

Signed-off-by: Roman Willi <roman.willi@ergon.ch>
@root30 root30 force-pushed the resource-customizations-microgateway-policies branch from c8d02c1 to eddfbc9 Compare June 15, 2026 07:39
@root30 root30 requested a review from crenshaw-dev June 15, 2026 14:02
Comment on lines +33 to +34
hs.status = "Healthy"
hs.message = (obj.kind or "Policy") .. " is healthy"

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My reading of this is that if any ancestor is healthy, we'll basically ignore any ancestors that are still progressing but that do not yet have the Accepted condition yet... Maybe the "Healthy" path should be a final loop that confirms that all ancestors are healthy?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants